closures: replace "is called" with "is defined" #2556
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Confusing "call" with "define" is especially unfortunate when
documenting closures.
The previous text was "... called in only ONE place ... we're still
calling the closure TWICE" - clearly wrong.
Also expand vague "define code" earlier in the page to the more
explicit "refer to
simulated_expensive_calculation
". "define code"was especially vague considering 1. this is dummy code that doesn't
really define anything, and 2. the code gets moved when changing
from function to closure.